Replacing the JSON Schema definition with an empty schema ({}) effectively disables validation for this type (it will accept any value). If these packages/spec/json-schema/** artifacts are meant to be generated, this looks like an accidental overwrite/regeneration issue and will likely break downstream consumers relying on constraints (required fields, enums, additionalProperties=false, etc.). Consider restoring the full schema content (or removing the file from version control and generating at publish time), and add a guard in the generation pipeline to avoid emitting empty definitions.

The new startsWith(resolvedAllowed) check is still vulnerable to prefix boundary issues (e.g., allowed /data/app also matches /data/app_evil) and can behave unexpectedly across platforms (path separators/case-sensitivity). A safer approach is to treat it as a path containment check: compute nodePath.relative(resolvedAllowed, resolvedPath) and ensure it does not start with .. and is not absolute, or require resolvedPath === resolvedAllowed OR resolvedPath.startsWith(resolvedAllowed + nodePath.sep).

This matches cap.metadata.hosts patterns against the full URL string, but the metadata key name strongly implies hostnames. This will incorrectly deny common inputs (e.g. host pattern api.example.com will never match https://api.example.com/path). It also risks subtle allow-bypass/deny errors if patterns start including scheme/path. Parse the URL (e.g., new URL(url).hostname) and match glob patterns against the hostname (and optionally port), keeping URL path matching as a separate capability if needed.

This matches cap.metadata.hosts patterns against the full URL string, but the metadata key name strongly implies hostnames. This will incorrectly deny common inputs (e.g. host pattern api.example.com will never match https://api.example.com/path). It also risks subtle allow-bypass/deny errors if patterns start including scheme/path. Parse the URL (e.g., new URL(url).hostname) and match glob patterns against the hostname (and optionally port), keeping URL path matching as a separate capability if needed.

This matches cap.metadata.hosts patterns against the full URL string, but the metadata key name strongly implies hostnames. This will incorrectly deny common inputs (e.g. host pattern api.example.com will never match https://api.example.com/path). It also risks subtle allow-bypass/deny errors if patterns start including scheme/path. Parse the URL (e.g., new URL(url).hostname) and match glob patterns against the hostname (and optionally port), keeping URL path matching as a separate capability if needed.

The path splitting/normalization is inconsistent on Windows (backslash patterns won’t reliably split into segments), and the regex escaping only handles . (other regex metacharacters like +()[]{}^$|\\ can change matching semantics). Consider first normalizing pattern to POSIX-style separators for matching, and escape all regex metacharacters before expanding glob tokens (*/**).

The path splitting/normalization is inconsistent on Windows (backslash patterns won’t reliably split into segments), and the regex escaping only handles . (other regex metacharacters like +()[]{}^$|\\ can change matching semantics). Consider first normalizing pattern to POSIX-style separators for matching, and escape all regex metacharacters before expanding glob tokens (*/**).

atob expects standard base64, but signatures in many ecosystems (notably JWT/JWS) are commonly base64url-encoded. If signature is base64url, this will fail verification even with correct keys. Consider normalizing base64url→base64 before decoding (replace -→+, _→/, add padding) and document the expected encoding for signature.

atob expects standard base64, but signatures in many ecosystems (notably JWT/JWS) are commonly base64url-encoded. If signature is base64url, this will fail verification even with correct keys. Consider normalizing base64url→base64 before decoding (replace -→+, _→/, add padding) and document the expected encoding for signature.

The metric 150 / 142 schemas is ambiguous/mismatched (test files > schemas). Consider rephrasing the table cells to explicitly separate counts, e.g. 150 test files / 142 schemas or 142/142 schemas covered and optionally list total tests separately (4,196) to avoid confusion.